chore(deps): Bump NATS.Net from 2.6.11 to 2.7.3#95
Conversation
--- updated-dependencies: - dependency-name: NATS.Net dependency-version: 2.7.3 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: NATS.Net dependency-version: 2.7.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
✅ This is a version-update:semver-minor update. Auto-merge has been enabled after CI passes. |
|
This pull request has been automatically marked as stale because it has not had recent activity. |
|
This pull request was automatically closed due to inactivity. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Updated NATS.Net from 2.6.11 to 2.7.3.
Release notes
Sourced from NATS.Net's releases.
2.7.3
Announcing a new version of NATS .NET client library covering various fixes and a security update on one dependency for NETStandard targets (#1089) even though the vulnerable API is not used by our library.
A big thank you to all NATS contributors and community members who helped make this release possible ❤️
Breaking Changes
NakAsync Signature Change (#1081)
The
TimeSpan delayparameter has been removed fromINatsJSMsg<T>.NakAsync(). The delay must now be passed viaAckOpts.NakDelay.Before (v2.7.2):
After (v2.7.3):
Note: because we also have an extension method, recompiling your project is enough.
AckTerminateAsync TermWithReason (#1048, #1081)
AckTerminateAsyncnow supports an optional termination reason. A new overload and a newTerminateReasonproperty onAckOptshave been added toINatsJSMsg<T>. Implementors of this interface must add the new method.Requires NATS Server 2.10.4+.
PinnedClient Validation (#1063)
Calling
NextAsync(),FetchAsync(), orFetchNoWaitAsync()on a consumer withPriorityPolicy.PinnedClientnow throwsNatsJSException. UseConsumeAsync()instead.Trade-offs of
SubPendingChannelCapacityYou should watch LOH memory usage and slow consumer events using
MessageDroppedhandler.Also note that channel doesn't allocate this immediately. The backing array grows twice as much each time there is need for more space.
Differences between
NatsClientandNatsConnectionNatsClientsetsSubPendingChannelFullModeoption toBoundedChannelFullMode.Waitby default which means you won't take advantage of this fix if you're usingNatsClientto setup your connection.If you are using
NatsClientthis fix won't affect your applications.... (truncated)
2.7.1
This is a patch fix release for NATS .NET client fixing breaking changes introduced in the previous minor release. With this release errors with transient dependencies that are referencing older versions of the client are corrected by using type forwarding since we moved serialization interfaces to a new 'Abstractions' assembly. We are planning to more other interfaces into the Abstractions assembly and we will make sure the type forwards are in place for those. We also had a fix for an OTel extension due to moving return types to interfaces.
What's Changed
Full Changelog: nats-io/nats.net@v2.7.0...v2.7.1
Big thanks to @caleblloyd and @heikkilamarko for their help finding and fixing these issues for everyone.
You can download this release from NuGet as usual: https://www.nuget.org/packages/NATS.Net/2.7.1
2.7.0
We are excited to announce a minor release of NATS .NET version 2.7.0 with a lot of fixes and improvements making NATS .NET client easier to use, testing friendly and more robust:
Important: Please note, there are also minor breaking changes which might affect dependent applications and sometimes transient dependencies. Application developers should recompile and test their application more rigorously in a non-production environment before deploying to production.
Breaking Changes
Timeout exceptions: Replaced OperationCanceledException with NatsTimeoutException for timeouts (previously surfaced as cancellations). Update any code catching OperationCanceledException for timeouts.
ReplyAsync on NatsJsMsg: Now marked [Obsolete]. Use the alternative method instead.
Serialization interface moved into abstractions: Via PR #858 ("Move Serialization Interface into Abstractions").
Fixed KV TTL interface handling (#854): This brings KV API inline with the design documents. It removed TTL parameters from update calls, which are problematic with buckets with history enabled.
New Features
Bug Fixes
What's Changed - Full List
OperationCanceledExceptionwithNatsTimeoutExceptionby @ealeykin in ReplaceOperationCanceledExceptionwithNatsTimeoutExceptionnats-io/nats.net#1022NatsJSConsumernever disposing receive activities (#911) by @aradalvand... (truncated)
2.7.0-preview.8
This is a bug fix and main merge release.
What's Changed
Full Changelog: nats-io/nats.net@v2.7.0-preview.7...v2.7.0-preview.8
Download from NuGet at https://www.nuget.org/packages/NATS.Net/2.7.0-preview.8
2.7.0-preview.7
This release aligns with the stable 2.6.10 release supporting new NATS Server version 2.12 features.
What's Changed
Full Changelog: nats-io/nats.net@v2.7.0-preview.6...v2.7.0-preview.7
Download from NuGet https://www.nuget.org/packages/NATS.Net/2.7.0-preview.7
2.7.0-preview.5
This release brings 2.7.x branch inline with main. There are important bug fixes. See release notes for 2.6.8 for details.
What's Changed
New Contributors
Full Changelog: nats-io/nats.net@v2.7.0-preview.4...v2.7.0-preview.5
Packages can be downloaded from NuGet: https://www.nuget.org/packages/NATS.Net/2.7.0-preview.5
2.7.0-preview.4
This is a patch preview release of NAT .NET client fixing a dispose and a consumer bug as well as providing corrections and improvements to interfaces.
What's Changed
New Contributors
Full Changelog: nats-io/nats.net@v2.7.0-preview.3...v2.7.0-preview.4
2.7.0-preview.3
Bug fix release and merges from main.
What's Changed
NatsJSConsumernever disposing receive activities by @aradalvand in fix:NatsJSConsumernever disposing receive activities nats-io/nats.net#911Full Changelog: nats-io/nats.net@v2.7.0-preview.2...v2.7.0-preview.3
2.7.0-preview.1
This is a new preview release with new features like the new Abstractions package.
What's Changed
FilterandEnrichfor OpenTelemetry activities by @aradalvand in Add support forFilterandEnrichfor OpenTelemetry activities nats-io/nats.net#859New Contributors
Full Changelog: nats-io/nats.net@v2.6.4...v2.7.0-preview.1
2.6.14
This is a bugfix release with a small but important Subject Validation feature. Subject validation is turned of by default and can be enabled in
NatsOpts. It will be enabled by default in a couple of releases down the line, so if you can, please enable it as soon as possible to make sure your applications are not affected. Subject validation makes sure subjects does not have whitespace characters as to not break the wire protocol. Placing spaces in subjects is not valid and well known. We do not expect the new subject validation feature to break any applications. Only being careful here. See #1017 for more details.What's Changed
Full Changelog: nats-io/nats.net@v2.6.12...v2.6.14
Packages can be downloaded from NuGet as usual: https://www.nuget.org/packages/NATS.Net/2.6.14
2.6.12
Happy to announce we have a new release of NATS .NET client library version 2.6.12. With this version we are providing several minor bug fixes and improvements as well as a couple of new features we missed out in our previous release supporting NATS Server 2.12: Support for
Nats-Expected-Last-Subject-Sequence-Subjectheader #1007 and prioritized mode #1011.Big thank you to our community for helping us with this release and to our contributors taking time to improve NATS .NET for everyone ❤️
What's Changed
New Contributors
Full Changelog: nats-io/nats.net@v2.6.11...v2.6.12
You can download the packages from NuGet: https://www.nuget.org/packages/NATS.Net/2.6.12
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)